SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Performance engineering</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Performance engineering</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

<p><b>Performance engineering</b> encompasses the techniques applied during a <a href="Systems_development_life_cycle" title="Systems development life cycle">systems development life cycle</a> to ensure the <a href="Non-functional_requirement" title="Non-functional requirement">non-functional requirements</a> for performance (such as <a href="Throughput" class="mw-redirect" title="Throughput">throughput</a>, <a href="Latency_(engineering)" title="Latency (engineering)">latency</a>, or <a href="Computer_memory" title="Computer memory">memory</a> usage) will be met. It may be alternatively referred to as <b>systems performance engineering</b> within <a href="Systems_engineering" title="Systems engineering">systems engineering</a>, and <b>software performance engineering</b> or <a href="Application_performance_engineering" title="Application performance engineering">application performance engineering</a> within <a href="Software_engineering" title="Software engineering">software engineering</a>.

</p><p>As the connection between application success and business success continues to gain recognition, particularly in the mobile space, application performance engineering has taken on a preventive and perfective<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> role within the software development life cycle. As such, the term is typically used to describe the processes, people and technologies required to effectively test non-functional requirements, ensure adherence to service levels and optimize application performance prior to deployment.

</p><p>The term <i>performance engineering</i> encompasses more than just the software and supporting infrastructure, and as such the term performance engineering is preferable from a macro view. Adherence to the non-functional requirements is also validated post-deployment by monitoring the production systems. This is part of <a href="IT_service_management" title="IT service management">IT service management</a> (see also <a href="ITIL" title="ITIL">ITIL</a>).

</p><p>Performance engineering has become a separate discipline at a number of large corporations, with tasking separate but parallel to systems engineering. It is pervasive, involving people from multiple organizational units; but predominantly within the <a href="Information_technology" title="Information technology">information technology</a> organization.

</p>

<div class="mw-heading mw-heading2"><h2 id="Performance_engineering_objectives">Performance engineering objectives</h2></div>

<ul><li>Increase business revenue by ensuring the system can process transactions within the requisite timeframe</li>

<li>Eliminate system failure requiring scrapping and writing off the system development effort due to performance objective failure</li>

<li>Eliminate late system deployment due to performance issues</li>

<li>Eliminate avoidable system rework due to performance issues</li>

<li>Eliminate avoidable system tuning efforts</li>

<li>Avoid additional and unnecessary hardware acquisition costs</li>

<li>Reduce increased <a href="Software_maintenance" title="Software maintenance">software maintenance</a> costs due to performance problems in production</li>

<li>Reduce increased software maintenance costs due to software impacted by ad hoc performance fixes</li>

<li>Reduce additional operational overhead for handling system issues due to performance problems</li>

<li>Identify future bottlenecks by simulation over prototype</li>

<li>Increase server capability</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Performance_engineering_approach">Performance engineering approach</h2></div>

<p>Because this discipline is applied within multiple methodologies, the following activities will occur within differently specified phases. However, if the phases of the <a href="IBM_Rational_Unified_Process" class="mw-redirect" title="IBM Rational Unified Process">rational unified process</a> (RUP) are used as a framework, then the activities will occur as follows:

</p><p>During the first, Conceptual phase of a program or project, critical <a href="Business_process" title="Business process">business processes</a> are identified. Typically they are classified as critical based upon revenue value, cost savings, or other assigned business value. This classification is done by the business unit, not the IT organization. High level risks that may impact system performance are identified and described at this time. An example might be known performance risks for a particular vendor system. Finally, performance activities, roles and deliverables are identified for the Elaboration phase. Activities and resource loading are incorporated into the Elaboration phase project plans.

</p>

<div class="mw-heading mw-heading3"><h3 id="Elaboration">Elaboration</h3></div>

<p>During this defining phase, the critical business processes are decomposed to critical <a href="Use_case" title="Use case">use cases</a>. Probe cases will be decomposed further, as needed, to single page (screen) transitions. These are the use cases that will be subjected to script driven <a href="Software_performance_testing" title="Software performance testing">performance testing</a>.

</p><p>The type of requirements that relate to performance engineering are the non-functional requirements, or NFR. While a functional requirement relates to which business operations are to be performed, a performance related non-functional requirement will relate to how fast that business operation performs under defined circumstances.

</p>

<div class="mw-heading mw-heading3"><h3 id="Construction">Construction</h3></div>

<p>Early in this phase a number of performance tool related activities are required. These include:

</p>

<ul><li>Identify key development team members as subject matter experts for the selected tools.</li>

<li>Specify a <a href="Profiler_(computer_science)" class="mw-redirect" title="Profiler (computer science)">profiling</a> tool for the development/component unit test environment.</li>

<li>Specify an automated unit (component) performance test tool for the development/component unit test environment; this is used when no GUI yet exists to drive the components under development.</li>

<li>Specify an automated tool for driving server-side unit (components) for the development/component unit test environment.</li>

<li>Specify an automated multi-user capable script-driven end-to-end tool for the development/component unit test environment; this is used to execute screen-driven use cases.</li>

<li>Identify a database test data load tool for the development/component unit test environment; this is required to ensure that the database optimizer chooses correct execution paths and to enable reinitializing and reloading the database as needed.</li>

<li>Deploy the performance tools for the development team.</li>

<li>Presentations and training must be given to development team members on the selected tools.</li></ul>

<p>The performance test team normally does not execute performance tests in the development environment, but rather in a specialized pre-deployment environment that is configured to be as close as possible to the planned production environment. This team will execute <a href="Software_performance_testing" title="Software performance testing">performance testing</a> against <a href="Test_case" title="Test case">test cases</a>, validating that the critical use cases conform to the specified non-functional requirements. The team will execute <a href="Load_testing" title="Load testing">load testing</a> against a normally expected (median) load as well as a peak load. They will often run <a href="Stress_testing_(software)" title="Stress testing (software)">stress tests</a> that will identify the system bottlenecks. The data gathered, and the analysis, will be fed back to the group that does <a href="Performance_tuning" title="Performance tuning">performance tuning</a>. Where necessary, the system will be tuned to bring nonconforming tests into conformance with the non-functional requirements.

</p><p>If performance engineering has been properly applied at each iteration and phase of the project to this point, hopefully this will be sufficient to enable the system to receive performance certification. However, if for some reason (perhaps proper performance engineering working practices were not applied) there are tests that cannot be tuned into compliance, then it will be necessary to return portions of the system to development for refactoring. In some cases the problem can be resolved with additional hardware, but adding more hardware leads quickly to diminishing returns.

</p>

<div class="mw-heading mw-heading3"><h3 id="Transition">Transition</h3></div>

<p>During this final phase the system is deployed to the production environment. A number of preparatory steps are required. These include:

</p>

<ul><li>Configuring the operating systems, network, servers (application, web, database, load balancer, etc.), and any message queueing software according to the base checklists and the optimizations identified in the performance test environment</li>

<li>Ensuring all performance monitoring software is deployed and configured</li>

<li>Running statistics on the database after the production data load is completed</li></ul>

<p>Once the new system is deployed, ongoing operations pick up performance activities, including:

</p>

<ul><li>Validating that weekly and monthly performance reports indicate that critical use cases perform within the specified non functional requirement criteria</li>

<li>Where use cases are falling outside of NFR criteria, submit defects</li>

<li>Identify projected trends from monthly and quarterly reports, and on a quarterly basis, execute <a href="Capacity_planning" title="Capacity planning">capacity planning</a> management activities</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Service_management">Service management</h2></div>

<p>In the operational domain (post production deployment) performance engineering focuses primarily within three areas: <a href="ITIL#Service_level_management" title="ITIL">service level management</a>, <a href="ITIL#Capacity_management" title="ITIL">capacity management</a>, and <a href="ITIL#Problem_management" title="ITIL">problem management</a>.

</p>

<div class="mw-heading mw-heading3"><h3 id="Service_level_management">Service level management</h3></div>

<p>In the service level management area, performance engineering is concerned with <a href="Service_level_agreement" class="mw-redirect" title="Service level agreement">service level agreements</a> and the associated systems monitoring that serves to validate service level compliance, detect problems, and identify trends. For example, when real user monitoring is deployed it is possible to ensure that user transactions are being executed in conformance with specified non-functional requirements. Transaction response time is logged in a database such that queries and reports can be run against the data. This permits trend analysis that can be useful for capacity management. When user transactions fall out of band, the events should generate alerts so that attention may be applied to the situation.

</p>

<div class="mw-heading mw-heading3"><h3 id="Capacity_management">Capacity management</h3></div>

<p>For capacity management, performance engineering focuses on ensuring that the systems will remain within performance compliance. This means executing <a href="Trend_analysis" title="Trend analysis">trend analysis</a> on historical monitoring generated data, such that the future time of non compliance is predictable. For example, if a system is showing a trend of slowing transaction processing (which might be due to growing data set sizes, or increasing numbers of concurrent users, or other factors) then at some point the system will no longer meet the criteria specified within the service level agreements. Capacity management is charged with ensuring that additional capacity is added in advance of that point (additional CPUs, more memory, new database indexing, et cetera) so that the trend lines are reset and the system will remain within the specified performance range.

</p>

<div class="mw-heading mw-heading3"><h3 id="Problem_management">Problem management</h3></div>

<p>Within the problem management domain, the performance engineering practices are focused on resolving the root cause of performance related problems. These typically involve system tuning, changing operating system or device parameters, or even refactoring the application software to resolve poor performance due to poor design or bad coding practices.

</p>

<div class="mw-heading mw-heading2"><h2 id="Monitoring">Monitoring</h2></div>

<p>To ensure that there is proper feedback validating that the system meets the NFR specified performance metrics, any major system needs a monitoring subsystem. The planning, design, installation, configuration, and control of the monitoring subsystem are specified by an appropriately defined monitoring process.

The benefits are as follows:

</p>

<ul><li>It is possible to establish service level agreements at the use case level.</li>

<li>It is possible to turn on and turn off monitoring at periodic points or to support problem resolution.</li>

<li>It enables the generation of regular reports.</li>

<li>It enables the ability to track trends over time, such as the impact of increasing user loads and growing data sets on use case level performance.</li></ul>

<p>The trend analysis component of this cannot be undervalued. This functionality, properly implemented, will enable predicting when a given application undergoing gradually increasing user loads and growing data sets will exceed the specified non functional performance requirements for a given use case. This permits proper management budgeting, acquisition of, and deployment of the required resources to keep the system running within the parameters of the non functional performance requirements.

</p>

<ul><li><a href="Java_performance" title="Java performance">Java performance</a></li>

<li><a href="Scalability" title="Scalability">Scalability</a></li>

<li><a href="Software_quality" title="Software quality">Software quality</a></li>

<li><a href="Software_testing" title="Software testing">Software testing</a></li>

<li><a href="Web_performance" title="Web performance">Web performance</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">"Banking Industry Lessons Learned in Outsourcing Testing Services," Gartner. August 2, 2012.</span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://docs.oracle.com/database/121/TGDBA/toc.htm">Database Performance Tuning Guide</a></li>

<li><a rel="nofollow" class="external text" href="http://www1.practicalperformanceanalyst.com">Practical Performance Analyst - Performance Engineering Community & Body Of Knowledge</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100106151249/http://www.mindtree.com/downloads/MindTree%20-%20Performance%20Engineering%20Flyer.pdf">Performance Engineering Methodology</a></li>

<li><a rel="nofollow" class="external text" href="http://www-128.ibm.com/developerworks/rational/library/4215.html">A Performance Engineering Strategy</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20090227123220/http://test.cmg.org/conference/cmg2004/awards/4083.pdf">A Performance Process Maturity Model</a></li>

<li><a rel="nofollow" class="external text" href="https://www.amazon.com/Every-Computer-Performance-Book-Computers/dp/1482657759/">The Every Computer Performance Book</a></li>

<li><a rel="nofollow" class="external text" href="http://webdiis.unizar.es/CRPetri/papers/jcampos/03_MC_SERP.pdf">Exploring UML for Performance Engineering</a></li>

<li><a rel="nofollow" class="external text" href="http://fortuitous.com/docs/primers/PE_Model_Intro.pdf">Introduction to Modeling Based Performance Engineering</a></li>

<li><a rel="nofollow" class="external text" href="http://www.ins.com/assets/A6BE9064-50DC-4E00-9B52-BA265DA722D6.pdf">Leveraging ITIL to Improve Application Performance</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120211011904/http://channel9.msdn.com/wiki/default.aspx/PerformanceWiki.PerformanceEngineering">Patterns & Practices Performance Engineering</a></li>

<li><a rel="nofollow" class="external text" href="http://www.perfeng.com/papers/pdcp.pdf">Performance and Scalability of Distributed Software Architectures</a></li>

<li><a rel="nofollow" class="external text" href="http://www.perfeng.com/papers/bestprac.pdf">Performance Engineering Best Practices (High Level)</a></li>

<li><a rel="nofollow" class="external text" href="http://delivery.acm.org/10.1145/340000/336553/p189-pooley.pdf?key1=336553&key2=4989881611&coll=GUIDE&dl=GUIDE,ACM&CFID=11111111&CFTOKEN=2222222">Software Engineering and Performance: A Road-map</a></li>

<li><a rel="nofollow" class="external text" href="http://fortuitous.com/docs/whitepapers/Performance_Cost.pdf">The Vicious Cycle of Computer Systems Performance and IT Operational Costs</a></li>

<li><a rel="nofollow" class="external text" href="http://blogs.technet.com/winserverperformance/">Microsoft Windows Server Performance Team</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100504044406/http://blogs.technet.com/winserverperformance/">Archived</a> 2010-05-04 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20131110055635/http://www.cmg.org/measureit/issues/mit23/m_23_2.html">Gathering Performance Requirements</a></li>

<li><a rel="nofollow" class="external text" href="http://sergeibaranov.sys-con.com/node/46513">Performance Testing Web Services: Strategies and Best Practices</a></li>

<li><a rel="nofollow" class="external text" href="http://www.cmg.org/measureit/issues/mit49/m_49_12.html">Performance Evaluation of an Air Traffic Control System using the Application Response Measurement (ARM) Standard</a></li>

<li><a rel="nofollow" class="external text" href="http://www.diplom.de/MA-Thesis__Master-17047/Integration_of_Performance_Management_into_the_Application_Lifecycle.html">Integration of Performance Management in ITIL</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Systems_engineering118" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Systems_engineering118" style="font-size:114%;margin:0 4em"><a href="Systems_engineering" title="Systems engineering">Systems engineering</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Subfields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Aerospace_engineering" title="Aerospace engineering">Aerospace engineering</a></li>

<li><a href="Biological_systems_engineering" title="Biological systems engineering">Biological systems engineering</a></li>

<li><a href="Cognitive_systems_engineering" title="Cognitive systems engineering">Cognitive systems engineering</a></li>

<li><a href="Configuration_management" title="Configuration management">Configuration management</a></li>

<li><a href="Earth_systems_engineering_and_management" title="Earth systems engineering and management">Earth systems engineering and management</a></li>

<li><a href="Electrical_engineering" title="Electrical engineering">Electrical engineering</a></li>

<li><a href="Enterprise_systems_engineering" title="Enterprise systems engineering">Enterprise systems engineering</a></li>

<li><a href="Health_systems_engineering" title="Health systems engineering">Health systems engineering</a></li>

<li><a href="Reliability_engineering" title="Reliability engineering">Reliability engineering</a></li>

<li><a href="Safety_engineering" title="Safety engineering">Safety engineering</a></li>

<li><a href="Stanford_torus" title="Stanford torus">Sociocultural Systems Engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Processes</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Requirements_engineering" title="Requirements engineering">Requirements engineering</a></li>

<li><a href="Functional_Analysis_and_Allocation" class="mw-redirect" title="Functional Analysis and Allocation">Functional Analysis and Allocation</a></li>

<li><a href="System_integration" title="System integration">System integration</a></li>

<li><a href="Verification_and_validation" title="Verification and validation">Verification and validation</a></li>

<li><a href="Design_review" title="Design review">Design review</a></li>

<li><a href="System_of_systems_engineering" title="System of systems engineering">System of systems engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Business_process" title="Business process">Business process</a></li>

<li><a href="Fault_tolerance" title="Fault tolerance">Fault tolerance</a></li>

<li><a href="System" title="System">System</a></li>

<li><a href="System_lifecycle" class="mw-redirect" title="System lifecycle">System lifecycle</a></li>

<li><a href="V-model" title="V-model">V-Model</a></li>

<li><a href="Systems_development_life_cycle" title="Systems development life cycle">Systems development life cycle</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Tools</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Decision-making" title="Decision-making">Decision-making</a></li>

<li><a href="Function_model" title="Function model">Function modelling</a></li>

<li><a href="Mathematical_optimization" title="Mathematical optimization">Optimization</a></li>

<li><a href="Quality_function_deployment" title="Quality function deployment">Quality function deployment</a></li>

<li><a href="Spare_part" title="Spare part">Spare part</a></li>

<li><a href="System_dynamics" title="System dynamics">System dynamics</a></li>

<li><a href="Systems_Modeling_Language" class="mw-redirect" title="Systems Modeling Language">Systems Modeling Language</a></li>

<li><a href="Systems_analysis" title="Systems analysis">Systems analysis</a></li>

<li><a href="Systems_modeling" title="Systems modeling">Systems modeling</a></li>

<li><a href="Work_breakdown_structure" title="Work breakdown structure">Work breakdown structure</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">People</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="James_S._Albus" title="James S. Albus">James S. Albus</a></li>

<li><a href="Ruzena_Bajcsy" title="Ruzena Bajcsy">Ruzena Bajcsy</a></li>

<li><a href="Benjamin_S._Blanchard" title="Benjamin S. Blanchard">Benjamin S. Blanchard</a></li>

<li><a href="Wernher_von_Braun" title="Wernher von Braun">Wernher von Braun</a></li>

<li><a href="Kathleen_Carley" title="Kathleen Carley">Kathleen Carley</a></li>

<li><a href="Harold_Chestnut" title="Harold Chestnut">Harold Chestnut</a></li>

<li><a href="Wolt_Fabrycky" title="Wolt Fabrycky">Wolt Fabrycky</a></li>

<li><a href="Barbara_Grosz" class="mw-redirect" title="Barbara Grosz">Barbara Grosz</a></li>

<li><a href="Arthur_David_Hall_III" title="Arthur David Hall III">Arthur David Hall III</a></li>

<li><a href="Derek_Hitchins" title="Derek Hitchins">Derek Hitchins</a></li>

<li><a href="Robert_E._Machol" title="Robert E. Machol">Robert E. Machol</a></li>

<li><a href="Radhika_Nagpal" title="Radhika Nagpal">Radhika Nagpal</a></li>

<li><a href="Simon_Ramo" title="Simon Ramo">Simon Ramo</a></li>

<li><a href="Joseph_Francis_Shea" title="Joseph Francis Shea">Joseph Francis Shea</a></li>

<li><a href="Katia_Sycara" title="Katia Sycara">Katia Sycara</a></li>

<li><a href="Manuela_M._Veloso" title="Manuela M. Veloso">Manuela M. Veloso</a></li>

<li><a href="John_N._Warfield" title="John N. Warfield">John N. Warfield</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related fields</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Control_engineering" title="Control engineering">Control engineering</a></li>

<li><a href="Computer_engineering" title="Computer engineering">Computer engineering</a></li>

<li><a href="Industrial_engineering" title="Industrial engineering">Industrial engineering</a></li>

<li><a href="Operations_research" title="Operations research">Operations research</a></li>

<li><a href="Project_management" title="Project management">Project management</a></li>

<li><a href="Quality_management" title="Quality management">Quality management</a></li>

<li><a href="Risk_management" title="Risk management">Risk management</a></li>

<li><a href="Software_engineering" title="Software engineering">Software engineering</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li>Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2022-09-15" href="https://en.wikipedia.org/wiki/?title=Performance_engineering&oldid=1110464472">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>